Hello I have two sites where I am moving local E2K3 mailboxes to new local E2K10 servers. In one site I can move any mailbox and all incoming email that comes in during the move to that mailbox just queues up and delivers once the move is complete. In my other site I get NDRs immediately once them move has started for both internal and expternal senders. The mail does not retry so never gets delivered. My mailboxes in that site get email 24x7 so I just cannot move them until I figure this out. Googled quite a bit and not finding anything. Anyone any ideas? NDRs look like this... Delivery has failed to these recipients or groups: Jane Doe <mailto:jdoe@domain.com> The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk. Diagnostic information for administrators: Generating server: server.domain.com jdoe@domain.com #< #4.4.7> #SMTP# Original message headers:

The process shouldn't NDR during the move. The NDR doesn't really say much to know the cause. Does the server have something else in front of it that could be generating the NDR? Antispam for example that is doing recipient validation by the mailbox being available, something like that? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Numeric Code: 4.4.7 Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This NDR may also indicate that a message header limit has been reached on a remote server or that some other protocol timeout occurred during communication with the remote server. What I find strange is that your mailflow (as I understand it) isn't altered. So, basically the problem should be the connection between the old 2003 Exchange and the new Exchange 2010. The recipient should be positively verified since mail flow first go to Exchange 2003 and recipient lookup to your AD should be ok, and delivery from 2003 to 2010 should start. I'm thinkting there might be connection issues from your second site to the Target Transport Server. Check your configuration with something like this: Get-RoutingGroupConnector -Identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\Ex2010 to Ex2003 RGC" and if you spot any you want to change, then use Set instead of Get ;-) Set-RoutingGroupConnectorJesper Bernle | Blog: http://xchangeserver.wordpress.com

Hi dazzerb, Per your description, the issue seems complicated. Per my known, when we move the mailbox between exchange2007/exchange2010 and exchange2010 server, we could achieve the online mailbox motion, I do no need worry about the email missed. If we move the mailbox from exchange 2003 to exchange 2010, the mailbox is offline, that means the mailbox of the account is set as disabled, so, the email sent to the mailbox would be queued in the queue, during the moverequest, the mailbox are moved to other site, but the message would be queued in the local deliver queue, so it will never could deliver to the remote site. Other work around, I would move all the mailboxes to the exchange 2010 server in the same site firstly, and then move it to other site, because if so, we could do the online move request, we do not need worry about the email missed. Regards! Gavin Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks everyone, Gavin-Zhang - we are only moving messages from 2003 to 2010 within the same site and never across sites. We have tried a few things (incl suggestions in this thread) and still only see this issue with one specific E2K3 server. We even see the problem moving the mailbox locally on that server. The box was been up for nearly 600 days so we are going to schedule an outage this weekend to reboot it and see if the problem resolves itself. If still persists we will call Microsoft. Thanks again - I will post the resolution once we know what it is.

Hi dazzerb, Thanks for your feedback, it is a good idea to open a ticket. Hope good news from you! Per your description, you referred the other site, so I maybe misunderstand your issue. Could you please describle more detailed about your scenario, it maybe related with message routing issue. Regards! Gavin Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Gavin we fixed the problem. We rebooted the Exchange 2003 server (it was up for 600 days) and the problem went away. When moving mailboxes now from this server to a new local E2K10 server we no longer get NDRs and messages deliver to the mailbox in about 40 minutes after the move is complete. So the reboot is all that was needed. I suspect that restarting the routing and SMTP services might have also fixed this. So it was really nothing in the end. Hope this post helps someone with same issue in future!